Bridge Definition/Data Entry Best Practice Guide

LEAP Bridge Concrete is a comprehensive bridge program capable of defining, analyzing and designing bridge geometry, superstructure and substructure via its various components.

Depending on the LEAP Bridge Concrete configuration you have, the bridge description can be started from any of the component applications: Bridge Parametric Layout, Precast/Prestressed Girder or CIP RC/PT Girder. Pier definition can be entered from Bridge Parametric Layout or Substructure, or by using the ABC Wizard within LEAP Bridge Concrete itself. In addition, LEAP Bridge Concrete can be used just to define, analyze and design a component of a bridge (beam, pier, etc.) without defining the whole bridge by running any one of the component programs independent of LEAP Bridge Concrete data interaction.

The decision to use LEAP Bridge Concrete in any of the above modes depends on the goal of the user at the time of use. The following sections provide best practice guides in the use of LEAP Bridge Concrete for various needs. It is important to understand that with LEAP Bridge Concrete there are always two data sets: one related directly to the component analysis and design, i.e. the native component file (Precast/Prestressed Girder, Substructure, etc.), and the LEAP Bridge Concrete database file for the entire bridge.

The best practices for LEAP Bridge are listed below, and further explained in individual sections following this listing: